Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New SatVu backend supporting SatVu's standard scene product (only one we have atm).
Notes
Needed to fix the missing values for type attribute of OpportunityFeature and OpportunityCollection. Not sure how that worked before but then again there's no dependency pinning... Also added basic logging setup because why not.
One thing to note about SatVu's opportunity/feasibility workflow: it's an async workflow which for the demo here is encapsulated sync flow of
find_opportunities
, which of course is not a good thing. A single request to STAT /opportunities will submit the feasibility request to SatVu's API and then poll SatVu's API until a final state is reached or a 60s timeout is reached.Starting the API with SatVu support
SatVu's APIs all need a contract ID, which for us is part of the API base path. Since there's no access to the incoming request by the backend implementation to check for an header for example, for this demo, the service picks it from the env. 🙈
Submitting a request
Needs a auth token, which issumed to be in the
TOKEN
env var when in this example with HTTPie:yields after roundabout 15s: